The Document Detail is always the first information displayed when entering the Document record. The Document Detail is displayed when the user selects the Document No. from the Doc Repository. The document tree is located to the left of the Document Detail and contains all other information regarding the document.
NOTE: Users utilizing Office Online for collaboration can click View Document in Collaboration in the menu bar to view the track changes of a document in collaboration.
Information | Description |
---|---|
Header |
The header of the Document record is always displayed at the top of the window and contains the following information:
|
Title |
Displays the title of the document. |
Master Copy Location |
Displays the location of the master copy of the document. |
Keep Copy Of Every Build |
Specifies whether or not a copy of every build of the document will be kept. If this is set to Yes, the system keeps previous copies of rejected documents prior to releasing the document after approval. If it is rejected, the build changes and a copy is stored in the database. |
Owner Role and Owner |
Each Document record contains an owner who is responsible for managing the activities within the Document record, such as authoring the document, managing approval, and managing changes. Document ownership can be changed at any time. |
Originator Code |
Displays the code of the user who created the document. |
Organization Unit |
The Org Unit is a business entity (Department, Customer, Supplier) that can be tied to the document for better searching and change control management. |
Product and Process |
A product and/or business/manufacturing operation that is tied to the document for better searching and change control management. |
Plant Area |
A Plant Area is a user defined field used to identify additional document information that can be used for searching and change control management. |
Review Group |
Review Groups can be predefined at the document type. They display users who need to approve the document and can be changed at any time from each document record. |
AutoExpire |
If this option is set to Yes, then the document will automatically expire on its expiration date. |
Dates |
Dates reflect the lifecycle of the document.
|
Supersede Previous Revision in Reference |
If this option is set to Yes, then each new revision of a document record replaces the previous revision of the document in the document’s References folder. |
Content Status |
This field indicates whether or not the native file of the document has been checked out and is being worked on. If the status indicates Checked Out, then the fields below will display which user has the file currently checked out. Users cannot checkout document files once they have been released (CURRENT). |
Secondary Format |
When a document is checked in, Document Management can automatically create a PDF file, known as a secondary file, of that document. This feature is referred to as AutoSync and though this setting is generally transferred from Document Type, it can be changed by the document owner. When activated, a cover page containing any important information for the document, such as Approval Signatures, Revision History, and Training Requirements, is also generated. NOTE: This feature can be exceptionally helpful during an audit if you need to print documents for auditors to view. |
Primary File Name |
The Primary File Name is the native (working) file. It is the file that is checked in and checked out whenever the document needs to be modified. When a file is checked out the system prompts the document author to save the file on their local workstation. Checking a file into the vault is similar to attaching a file to an email. |
Secondary File Name |
The Secondary File Name is the viewing (PDF) file. It is the file that is rendered to PDF automatically using AutoSync or manually by the document owner. Most end-users only have rights to view the Secondary File, not the Primary File. It is up to you to decide who has access to the files. |
See Also
Accessing the Document Repository
|